Systems for information sharing and methods of use, discussion and collaboration system and methods of use

ABSTRACT

A collaborative and communication system is presented. The collaborative technology can be applied to enable team members and customers to discuss and collaborate over a document, document content, and the like through voice recording and/or voice and video meetings. In this way, an application and associated functionality and features for document discussions in a dynamically generated format is provided. In this way, support incident by forming a document and/or pdf document and/or image based on a support incident and various properties can be generated. Furthermore, the present disclosure provides for recording of audio and video in association with annotation of a document and/or annotation of drawings, and the like. Furthermore, the system provides for document discussion and annotation in real time and for collaboration and dynamically generating documents—documents which represent various task properties, and support incident properties—all with voice recording, animation, and drawing.

CROSS-REFERENCE TO RELATED APPLICATIONS

The present application claims priority to the U.S. Utility patentapplication Ser. No. 17/587,030 which was filed on Jan. 28, 2022, whichis hereby incorporated by reference herein in its entirety, includingany figures, tables, or drawings.

The present application claims priority to the U.S. Provisional PatentApplication No. 61/576,389 which was filed on Dec. 16, 2011, which ishereby incorporated by reference herein in its entirety, including anyfigures, tables, or drawings.

FIELD OF THE DISCLOSURE

This disclosure relates to a system for converting business objects,objects, and content into a live document, or livedoc. Furthermore, thisdisclosure relates to a system for information sharing and a method ofuse. Furthermore, and without limitation, this disclosure relates to adiscussion and collaboration system and methods of use.

COPYRIGHT NOTICE

At least a portion of the disclosure of this patent document containsmaterial that is subject to copyright protection. The copyright ownerhas no objection to the facsimile reproduction by anyone of the patentdocument or the patent disclosure, as it appears in the Patent andTrademark Office patent files and/or records, but otherwise reserves allcopyright rights whatsoever. The following notice applies to thesoftware and data as described below and in the drawings that form apart of this document. Copyright. Tieren Zhou. All rights reserved.

BACKGROUND OF THE DISCLOSURE

In recent times, cloud computing service providers deliver applicationsvia the internet. Such cloud supported applications can be accessed ondesktops or mobile devices via web browsers, while the operationalsoftware and data are stored on servers at some remote location(s) inthe “cloud”. One of the promising application areas in the context ofcloud computing is information sharing among different users because the“cloud” enables a user to access systems or applications via a webbrowser regardless of the location of or device type the user is using.As the backbone supporting infrastructure is off-site (typicallyprovided by a third-party) and accessed via the Internet, a user canvirtually connect to an application from anywhere. Early examples inthis area include screen-sharing applications where one person's screencan be encoded video stream and real-time delivered to other persons. Inother examples, business applications have been coded entirely usingweb-based technologies. In still another example, business applicationsfor information sharing are often developed using web-based technologieswhere information is shared using web browsers.

Traditionally, people share information online through means such asemail, instant messenger, message board, desktop sharing, etc., whichmay not be effective and efficient, especially when multiple parties areinvolved and when the shared information includes multimediainformation. For example, traditional online meeting based onscreen-sharing may introduce a significant latency because it requirestransferring the desktop information of the presenter in the form of avideo stream to each of the participants. Moreover, currently, there isno effective cloud-based platform for multiple users to modify sharedinformation in a simple and straightforward manner and consolidatemodifications to the shared information from different users in anintuitive form. Therefore, there is a need to provide a solution forsharing multimedia information with an improved user experience.

Thus, there is a long-felt need in the art for collaborative technology,as described further herein, which can be applied to enable team membersand customers to discuss and collaborate over a document, documentcontent, and the like through voice recording and/or voice and videomeetings. In the present disclosure, as will become more clear asfurther described herein, the present disclosure provides an applicationand associated functionality and features for document discussions in adynamically generated format.

In this way, the present disclosure also provides for support incidentby forming a document and/or pdf document and/or image based on asupport incident and various properties. Furthermore, the presentdisclosure provides for recording of audio and video in association withannotation of a document and/or annotation of drawings, and the like. Inthis way, the present disclosure provides for document discussion andannotation in real time and in collaboration. Furthermore, the presentdisclosure provides for dynamically generating documents—documents whichrepresent various task properties, and support incident properties, andthe like. Furthermore, the present disclosure provides for voicerecording, animation, and drawing, and the like.

The disclosure herein provides these advantages and others as willbecome clear from the specification and claims provided.

SUMMARY OF THE DISCLOSURE

The present disclosure provides a system for converting content into alive document. The live document can then be used to create syncmeetings or live meetings, and more. The present disclosure relates to asystem for information sharing and a method of use. Furthermore, andwithout limitation, this disclosure relates to a discussion andcollaboration system and methods of use.

Particularly, the present disclosure is directed to a collaborativetechnology, as described further herein, which can be applied to enableteam members and customers to discuss and collaborate over a document,document content, and the like through voice recording and/or voice andvideo meetings. In the present disclosure, as will become more clear asfurther described herein, the present disclosure provides an applicationand associated functionality and features for document discussions in adynamically generated format.

In this way, the present disclosure also provides for support incidentby forming a document and/or pdf document and/or image based on asupport incident and various properties. Furthermore, the presentdisclosure provides for recording of audio and video in association withannotation of a document and/or annotation of drawings, and the like. Inthis way, the present disclosure provides for document discussion andannotation in real time and in collaboration. Furthermore, the presentdisclosure provides for dynamically generating documents—documents whichrepresent various task properties, and support incident properties, andthe like. Furthermore, the present disclosure provides for voicerecording, animation, and drawing, and the like.

In the arrangement shown, as one example, a system for informationsharing and a method of use are presented—and a discussion andcollaboration system and methods of use are presented. The presentdisclosure provides the state of the art with a technology that can beapplied to enable team members and customers to interactively anddynamically discuss and collaborate over document content.

In this way, teams and customers can interact dynamically via voicerecording and live meetings, including video and pre-edited documents—itdesired. In this way, the present disclosure also provides forgenerating a document from a support incident and can also form a pdf oran image based on the support incident.

In this way, information can be shared and later recalled in the exactmanner it was discussed. In this way, the present disclosure providesclarity in ongoing matters and enhances communication of subject matter.

Furthermore, and in the arrangements shown, the present disclosure alsoprovides for voice recording and animation of documents and documentsinformation. This includes annotation of the drawings.

In the present disclosure, documents can be viewed, dynamically editedand/or annotated in real time. Furthermore, documents which are reviewedand/or generated can represent task properties and various supportincidents properties. Furthermore, voice recording can be overlayed onlive information and also animation and drawing of documents.

Furthermore, the present disclosure provides an asynchronous means ofcommunicating by various users. This enhanced communication and thevarious features provided herein change the state of the art and theability to collaborate, especially from remote geographic locations.Said another way, the present disclosure provides the ability totransmit to remote users the ability to view the content whether live orpre-recorded.

Thus, it is a primary object of the disclosure to provide a system forinformation sharing and a method of use are presented—and a discussionand collaboration system and methods of use that improve upon andenhance the state of the art.

Another object of the disclosure is to provide a system for informationsharing and a method of use are presented—and a discussion andcollaboration system and methods of use that provides for generation andimplementation of a support ticket.

Yet another object of the disclosure is to provide a system forinformation sharing and a method of use are presented—and a discussionand collaboration system and methods of use that can display a pluralityof objects in a single view.

Another object of the disclosure is to provide a system for informationsharing and a method of use are presented—and a discussion andcollaboration system and methods of use that provides call centerfunctionality in which all meeting requests between teams and customersare represented as object tiles.

Yet another object of the disclosure is to provide a system forinformation sharing and a method of use are presented—and a discussionand collaboration system and methods of use that enhances communicationand success of call centers.

Another object of the disclosure is to provide a system for informationsharing and a method of use are presented—and a discussion andcollaboration system and methods of use that enhances the communicationand success of supporting agents.

Yet another object of the disclosure is to provide a system forinformation sharing and a method of use are presented—and a discussionand collaboration system and methods of use that enhances thecommunication and success of ticketing systems.

Another object of the disclosure is to provide a system for informationsharing and a method of use are presented—and a discussion andcollaboration system and methods of use that enhances the communicationand success of ALM and project management.

Yet another object of the disclosure is to provide a system forinformation sharing and a method of use are presented—and a discussionand collaboration system and methods of use that enhances thecommunication and success of event management and event managementplatforms.

These and other objects, features, or advantages of the presentdisclosure will become apparent from the specification and claims.

BRIEF DESCRIPTION OF THE DRAWINGS

The methods, systems, and/or programming described herein are furtherdescribed in terms of exemplary embodiments. These exemplary embodimentsare described in detail with reference to the drawings. Theseembodiments are non-limiting exemplary embodiments, in which likereference numerals represent similar structures throughout the severalviews of the drawings, and wherein:

FIG. 1 is a high level exemplary diagram of a system for informationsharing, according to an embodiment of the present teaching;

FIG. 2(a) is a more detailed diagram of the exemplary system forinformation sharing shown in FIG. 1, according to different embodimentsof the present teaching;

FIG. 2(b) is a more detailed diagram of the exemplary system forinformation sharing shown in FIG. 1, according to different embodimentsof the present teaching;

FIG. 3(a) is a depiction of an exemplary application of a system forinformation sharing, according to different embodiments of the presentteaching;

FIG. 3(b) is a depiction of an exemplary application of a system forinformation sharing, according to different embodiments of the presentteaching;

FIG. 3(c) is a depiction of an exemplary application of a system forinformation sharing, according to different embodiments of the presentteaching;

FIG. 3(d) is a depiction of an exemplary application of a system forinformation sharing, according to different embodiments of the presentteaching;

FIG. 3(e) is a depiction of an exemplary application of a system forinformation sharing, according to different embodiments of the presentteaching;

FIG. 3(f) is a depiction of an exemplary application of a system forinformation sharing, according to different embodiments of the presentteaching;

FIG. 3(g) is a depiction of an exemplary application of a system forinformation sharing, according to different embodiments of the presentteaching;

FIG. 4 is a diagram of an exemplary information sharing controller of asystem for information sharing, according to an embodiment of thepresent teaching;

FIG. 5 is a depiction of an exemplary non-time-based supporting objectand time-based supporting object, according to an embodiment of thepresent teaching;

FIG. 6 is a depiction of an exemplary process of synchronizingsupporting objects with a base object, according to an embodiment of thepresent teaching;

FIG. 7 is a depiction of another exemplary process of synchronizingsupporting objects with a base object, according to an embodiment of thepresent teaching;

FIG. 8(a) is a flowchart of exemplary processes of information sharing,according to different embodiments of the present teaching;

FIG. 8(b) is a flowchart of exemplary processes of information sharing,according to different embodiments of the present teaching;

FIG. 9 is an exemplary diagram of a system for online meeting, accordingto an embodiment of the present teaching;

FIG. 10 is a depiction of an exemplary process of online meeting,according to an embodiment of the present teaching;

FIG. 11(a) is a flowchart of an exemplary process of online meeting,according to different embodiments of the present teaching;

FIG. 11(b) is a flowchart of an exemplary process of online meeting,according to different embodiments of the present teaching;

FIG. 12 depicts a general computer architecture on which the presentteaching can be implemented;

FIG. 13 depicts a general timeline and/or computer appearance of anexample of a timeline for which a document might be produced, thedocument might be enhanced, and collaborations may take place and thepresent teaching can be implemented;

FIG. 14 depicts a general timeline and/or computer appearance of anexample of a timeline for which a document might be produced, thedocument might be enhanced, and collaborations may take place and thepresent teaching can be implemented;

FIG. 15 depicts a general computer architecture and appearance on whichthe present teaching can be implemented and actions such as meetingactions can take place;

FIG. 16 depicts a general computer architecture and appearance on whichthe present teaching can be implemented and actions such as meetingactions can take place;

FIG. 17 is a depiction of an exemplary process of online meeting,according to an embodiment of the present teaching;

FIG. 18 is a depiction of an exemplary process of online meeting,according to an embodiment of the present teaching;

FIG. 19 is a depiction of an exemplary process of online meeting,according to an embodiment of the present teaching;

FIG. 20 is a depiction of an exemplary process of online meeting,according to an embodiment of the present teaching;

FIG. 21 is a depiction of an exemplary process of online meeting,according to an embodiment of the present teaching.

DETAILED DESCRIPTION OF THE DISCLOSURE

In the following detailed description, reference is made to theaccompanying drawings which form a part hereof, and in which is shown byway of illustration specific embodiments in which the disclosure may bepracticed. These embodiments are described in sufficient detail toenable those skilled in the art to practice the disclosure, and it is tobe understood that other embodiments may be utilized and thatmechanical, procedural, and other changes may be made without departingfrom the spirit and scope of the disclosure(s). The following detaileddescription is, therefore, not to be taken in a limiting sense, and thescope of the disclosure(s) is defined only by the appended claims, alongwith the full scope of equivalents to which such claims are entitled.

As used herein, the terminology such as vertical, horizontal, top,bottom, front, back, end, sides and the like are referenced according tothe views, pieces and figures presented. It should be understood,however, that the terms are used only for purposes of description, andare not intended to be used as limitations. Accordingly, orientation ofan object or a combination of objects may change without departing fromthe scope of the disclosure.

Reference throughout this specification to “one embodiment,” “anembodiment,” “one example,” or “an example” means that a particularfeature, structure, or characteristic described in connection with theembodiment or example is included in at least one embodiment of thepresent disclosure. Thus, the appearance of the phrases “in oneembodiment,” “in an embodiment,” “one example,” or “an example” invarious places throughout this specification are not necessarily allreferring to the same embodiment or example. Furthermore, the particularfeatures, structures, databases, or characteristics may be combined inany suitable combinations and/or sub-combinations in one or moreembodiments or examples. In addition, it should be appreciated that thefigures provided herewith are for explanation purposes to personsordinarily skilled in the art and that the drawings are not necessarilydrawn to scale.

Embodiments in accordance with the present disclosure may be embodied asan apparatus, method, or computer program product. Accordingly, thepresent disclosure may take the form of an entirely hardware-comprisedembodiment, an entirely software-comprised embodiment (includingfirmware, resident software, micro-code, etc.), or an embodimentcombining software and hardware aspects that may all generally bereferred to herein as a “circuit,” “module,” or “system.” Furthermore,embodiments of the present disclosure may take the form of a computerprogram product embodied in any tangible medium.

Any combination of one or more computer-usable or computer-readablemedia may be utilized. For example, a computer-readable medium mayinclude one or more of a portable computer removable drive, a hard disk,a random access memory (RAM) device, a read-only memory (ROM) device, anerasable programmable read-only memory (EPROM or Flash memory) device, aportable compact disc read-only memory (CDROM), an optical storagedevice, and a magnetic storage device. Computer program code forcarrying out operations of the present disclosure may be written in anycombination of one or more programming languages. Such code may becompiled from source code to computer-readable assembly language ormachine code, or virtual code, or framework code suitable for thedisclosure herein, or machine code suitable for the device or computeron which the code will be executed.

Embodiments may also be implemented in cloud computing environments. Inthis description and the following claims, “cloud computing” may bedefined as a model for enabling ubiquitous, convenient, on-demandnetwork access to a shared pool of configurable computing resources(e.g., networks, servers, storage, applications, and services) that canbe rapidly provisioned via virtualization and released with minimalmanagement effort or service provider interaction and then scaledaccordingly. A cloud model can be composed of various characteristics(e.g., on-demand self-service, broad network access, resource pooling,rapid elasticity, and measured service), service models (e.g., Softwareas a Service (“Saas”), Platform as a Service (“PaaS”), andInfrastructure as a Service (“IaaS”)), and deployment models (e.g.,private cloud, community cloud, public cloud, and hybrid cloud).

The flowchart and block diagrams in the attached figures illustrate thearchitecture, functionality, and operation of possible implementationsof systems, methods, and computer program products according to variousembodiments of the present disclosure. In this regard, each block in theflowchart or block diagrams may represent a module, segment, or portionof code, which comprises one or more executable instructions forimplementing the specified logical function(s). It will also be notedthat each block of the block diagrams and/or flowchart illustrations,and combinations of blocks in the block diagrams and/or flowchartillustrations, may be implemented by special purpose hardware-basedsystems that perform the specified functions or acts, or combinations ofspecial purpose hardware and computer instructions. These computerprogram instructions may also be stored in a computer-readable mediumthat can direct a computer or other programmable data processingapparatus to function in a particular manner, such that the instructionsstored in the computer-readable medium produce an article of manufactureincluding instruction means which implement the function/act specifiedin the flowchart and/or block diagram block or blocks.

In the arrangement shown, as one example, a system for quickly andefficiently converting content into a live document is presented. Thelive document can then be used to create sync meetings or live meetings,and more. In the arrangement shown, as a couple of many examples,objects, or business objects may include, but are not limited to, salesquotes in a sales application, tickets in a customer supportapplication, website images, content, or even videos. Said another way,a system for information sharing is presented. Furthermore, a system forinformation sharing and a method of use are provided. Furthermore, asystem for information sharing, method of use, a discussion andcollaboration system and method of use are also presented.

In the arrangement shown, as one example, the system for informationsharing presented provides the state of the art with an information andcollaboration system which enhances and enables efficiencies that didnot previously exist in the art. Said another way, the presentdisclosure provides a collaboration system which provides for real-timeand recording of communications which easily communicate information forcollaborators—including but not limited to user, clients, customers,technicians, employees, friends, co-workers, and the like.

In the arrangement shown, as one example, an information sharing systemis provided which enhances clarity and understanding in communicationwhich makes fixing technical issues and the like easier. This is onlyone example, as the present disclosure is not limited to technicalissues. The present disclosure may be utilized in a variety of fieldsand applications, as will become apparent from the disclosure. Forexample, the present disclosure may be used between a business and abusiness, a business and potential client, a business and a client, ateam of marketers, a team of employees, a plurality of techniciansworking with clients to fix technical or IT problems, and many otherapplications.

In this way, the present disclosure provides efficiencies incommunications, especially in providing understanding of communication,dramatically improving time spent in diagnosing and/or fixing issues,and more.

In summary, the present disclosure provides the ability for a user toeasily create content which aids in communication. This content may beto tell someone what a problem is, to communicate to another aboutchanges requested, or simply to relay and provide understanding ininformation. For these reasons, it quickly will become clear that thisdisclosure can be used across a variety of fields from teaching, to IT,to marketing, to others. In this way, the present disclosure providestremendous value to any user because of enhanced communication andsatisfying results in knowing that a subsequent collaborator has viewedand/or worked with the present and/or solved issues—as will become moreclear from the present disclosure.

The present disclosure also provides a history of communication, theability to record over previous syncs and the like. The presentdisclosure also provides a log of history related to syncs, and thelike. Livesync also has an ongoing history and log—keeps track ofprevious syncs, previous uploads of content, and ability for agents andthe like to review back. Furthermore, the present disclosure providesimproved collaboration, improved issue solving and/or problem solving.Importantly, the present disclosure provides for an information systemsharing which is more than a one-way street. In other words, variouscollaborators can communicate over the same content and easily re-enablepreviously recorded syncs to work on top of.

These advantages, features, and functionalities will be elaborated on,expanded upon, and more understood in the present disclosure.

System:

With reference to the figures, a system for information sharing and amethod of use are presented—and a discussion and collaboration systemand methods of use are presented. Information sharing system is formedof any suitable size, shape and design having various features andfunctionality.

As one example, the information sharing system may be utilized on awebsite. Existing websites in the state of the art provide informationsharing by providing static images and static text to communicate. Inthis way, existing websites and similar try to present material in astatic way to communicate with potential clients and others learningabout the company, and the like. The present disclosure transformswebsites, and similar to be interactive, and enhances communication andunderstanding.

In this example, the information sharing system disclosed hereinprovides presentations, voice recordings, and annotations instead ofonly static images or static content or any content on a website,videos, or the like. With livesync enabled on a website, a visitor isenabled to also request live support, live help, a visitor can start alivesync meeting, other collaborators of the visitor and the websiterepresentative can all join. In this way, a visitor can start a newmeeting to discuss certain content and/or topic of interest. While avisitor is waiting for someone to join, they can create their owncontent, they can also upload additional content to have additionalcontent available for representatives. More resources than a simpleimage or viewing a static image. Creates collaboration in real time forcustomers and clients, other collaborators, and more.

As another example—of the many examples—livesync and the informationsharing system disclosed herein might be used in a customer supportsystem environment. In this example, a customer can login to a portal asa customer of an entity for a service, etc. Once logged in can view openissues, tickets, livesync updates (for previous livesyncs) or can entera new issue. In one example, a user and/or client may be using asoftware, but perhaps a button of the interface and/or software is notworking.

In this example, a customer and/or user might provide a description ofthe problem in creating a new ticket and/or creation of a new livesync.Common problems with typical support issues like this are additionalcalls and additional screen sharing just to figure out the issue (Notall industries provide for screen sharing, etc.). Some customers, atbest, might at least attach a screenshot. Most customers just wantissues resolved and may not be highly technically skilled or familiarwith a particular program, or the like. Even with screenshots,interpretation and lots of additional communication to resolve issues.

The present disclosure provides the state of the art with a system inwhich a customer can record the issue while voicing the issue, etc. Thisconveys and explains the problem more clearly to a technician. In turn,a technician can understand what the problem and/or is and can easilydiagnose that problem in significantly less time with less communicationand less effort, especially with highlighting done to highlight aparticular problem.

In this example, as continued, if a customer doesn't want to use ascreenshot or perhaps is unable to use a screenshot, screen sharing isan option through livesync. Additionally, the support team and/orcollaborator can walk through with clients on content and applicationsin real time. This enhances offering clarity in understanding and makesfixing technical issues and the like extremely more efficient than thecurrent state of the art. In this way, diagnostic time can bedramatically reduced with simple livesync by a customer. Support agentsand/or collaborators can playback issues and/or playback livesyncs whichwere provided, share those livesyncs with others for second or thirdopinions and/or assistance, and prepare new sync for customers withresolutions, and the like.

These and other examples will become apparent through the presentdisclosure.

In the arrangement shown, as one example, information sharing system maycomprise remote servers, databases, application servers, applicationdatabases, product databases, mobile applications, and/or computers; allof which in continuity or as separate acts fulfill the functionsdisclosed herein.

In the arrangement shown, as one example, the main structure of system10 also includes a plurality of users and/or collaborators, a pluralityof content, a sync, a syncroom, a livesync, and a computing platform,and communication and control components, among other components,features, and functionality.

Users/Collaborators (or Plurality Thereof):

In the arrangement shown, as one example, an information sharing systemincludes at least one user or at least one collaborator. User orcollaborator may be any user interacting with or utilizing theinformation sharing system—whether the collaborator is creating syncs,sharing syncs, reviewing syncs, listening in on livesyncs, and the like.Furthermore, this may include viewing, controlling, analyzing,manipulating, and/or interacting with the information sharing system,the content, a plurality of syncs, a syncroom, a livesync, or the like.User and/or collaborator is not limited to a single user but may be aplurality of users and/or a plurality of collaborators.

Content:

In the arrangement shown, as one example, the information sharing systemincludes a plurality of content. Content is formed of any suitableinformation sharing content and is incorporated, uploaded, or createdwithin the system. Content includes, but is not limited to a pdf, a worddocument, an image file, a combination thereof, and the like. Contentmay include audio, or may have audio and the like added to it. Contentmay also include a live webscreen or interface of a software applicationand the like in which a collaborator can view, and overlay with a voiceand/or audio recording. Similarly, this content may be annotated and thelike and may also include video from a recording such as a phone and/orsmart device video or image capture.

Sync (synchronous collaboration—not done in real time, solo or voicerecording; syncs against a live doe): In the arrangement shown, and atthe heart of the communication and/or information sharing system is a“sync”. A sync is a recording in which a collaborator records audio orvideo and/or a combination of these in order to share information. Async is generally not done in real time but is created by a user and/orplurality users for the purpose of explaining information andsubsequently sharing this information or sync with another and/or aplurality of subsequent collaborators.

Viewable Content of Sync: A sync may include viewing content. In thisway, viewing content may be screen recording, an online video, ascreenshot, a graphical user interface, a capture image, a capturedvideo, a combination of die like, or similar.

Audio Content of Sync: Sync provides a communication tool for thepurpose of sharing information. For this purpose, audio content is oftenincorporated into a sync. This audio content provides explanations,communications, question asking, explanations, guidance, directions, andmore. Audio content is not always strictly audio content but may beother forms of communication content such as typed content, chats,annotations through words, a combination thereof, and the like.

Annotation Content of Sync: Sync provides for a variety of annotationtypes. Some annotation types include, but are not limited tohighlighting, sticky notes (with typed communication), embeddingobjects—such as video links or web links, voice recordings asannotations, a combination thereof, and other annotations for thepurpose of clarifying information.

These annotations and other information are recorded as part of the syncand/or become part of the document which can be shared with others.Additionally, these syncs can be subsequently acted upon, and/orinformation can be overlaid. For example, a previous audio recording maybe quieted and/or removed so that a new audio can be overlaid on theprevious sync to answer questions about a particular point in a videosync or the like. In this way, information shared can be furtherelaborated on, answered, and more. In this way, a plurality of syncsrelated to a particular topic, or the like can be created. Variousaudience members can overlay their own sync on a previous sync.“subsequent sync”.

Syncrooms: or a plurality of syncs and/or a history log related to thesame topic. These annotations and the like described herein, and otherinformation are recorded as part of the sync and/or become part of thedocument which can be shared with others. Additionally, these syncs canbe subsequently acted upon, and/or information can be overlaid. Forexample, a previous audio recording may be quieted and/or removed sothat a new audio can be overlaid on the previous sync to answerquestions about a particular point in a video sync or the like. In thisway, information shared can be further elaborated on, answered, andmore. In this way, a plurality of syncs related to a particular topic,or the like can be created. Various audience members can overlay theirown sync on a previous sync. “subsequent sync”.

In this way, topics and/or channels for certain topics or even multipletopics can be organized into a particular location for access (and evensubsequent sharing of information). Collaborations on a particulartopic, often might need to be accessed more than once. For example, ifthere is a common error that users need assistance with, then atechnician may share a particular syncroom with that user rather thanrecreating a sync which was previously created or addressed. Syncroomshave this purpose and many others which further aid in informationsharing, and information organization, and the like.

In this way, previously created content may be searched if it is alreadywithin a syncroom, and more. Furthermore, and said another way,syncrooms provided a centralized location for content. Furthermore, andsaid another way, syncrooms provide for easily finding material andcontent, and easily finding related content. Furthermore, and saidanother way, syncrooms also provide a real time chat feature within asyncroom. Furthermore, meetings and the like can be created directlyfrom a syncroom setting.

LiveSync:

A livesync is a type of sync. A livesync further enhances on theadvantages of a sync by providing the livesync for a plurality ofcollaborators in real time. In other words, a livesync provides forinstant interaction of a sync for enhanced communication and informationsharing, and the like. Said another way, livesyncs provide tremendousvalue because this can also work across various industries. Livesyncalso provides satisfaction for customers and users as being heard—it canbe very satisfying to see that technicians are looking at problems andproviding a review of the sync and providing resolution through a sync,so customers can play back and feel like they have been heard, and/orconfirm they have been heard and understood properly.

A livesync may be a single instance of a syncroom, or a sync.Furthermore, a livesync may be a plurality of livesyncs and appear as aseries of meetings which can also be reviewed and further elaboratedupon. Said another way, livesyncs also provide an ongoing history andlog—keeps track of previous syncs, previous uploads of content, andability for agents and the like to review back.

System for Information Sharing:

FIG. 1 is an exemplary example of a high-level exemplary system diagramof a system for information sharing and the disclosures providedherein—according to an embodiment of the present teaching. Theinformation-sharing system 100 may reside on a “cloud” computingenvironment formed by distributed and shared computing resourcesconnected through a set of networks. The networks can be a singlenetwork or a combination of different networks. For example, a networkcan be a local area network (LAN), a wide area network (WAN), a publicnetwork, a private network, a proprietary network, a Public TelephoneSwitched Network (PSTN), the Internet, a wireless network, a virtualnetwork, or any combination thereof. Users may share information (e.g.,documents, ideas, etc.) Through the information sharing system 100residing on the “cloud.

The information-sharing system 100 in this example includes aninformation sharing controller 102, an information database 104, and auser database 106. The information sharing controller 102 is a mechanismfor controlling operations of the information sharing system 100 andwill be described in detail later. The information database 104 mayinclude one or more databases on one or more servers for providing andstoring any information to be shared among users. For example, at leastthree categories of information are stored in the information database104: base objects, supporting objects and synchronizing actions.

The base objects may be converted user files of a certain type that canbe accessed by any user via a web browser or an application. Forexample, the user files may carry on information that the users want toshare through information sharing system 100 and include, but are notlimited to, text, presentation slide, images, music sheet, spreadsheet,video, portable document format (PDF) file, database file, or anysuitable type of file known in the art. The user files may not bedirectly accessed by different web browsers, operating systems, orapplications and thus, may need to be converted to the base objects of acertain type. For example, the base object may be an ADOBE FLASH file, AMICROSOFT SILVERLIGHT file, an HTML5 file, and image file, a video file,a PDF file, or any suitable type of file known in the art.

The supporting objects may be generated based on information provided bythe users in view of the base objects and associated with thecorresponding base objects. For example, the supporting objects maycomment on the base object provided by the same user or a differentuser, in the forms of, for example, a text note, a text comment, ahighlighting box, and audio comment, etc. Depending on the way in whichthe supporting objects are associated with the base objects, thesupporting objects may include time-based supporting object, such as anaudio, a video, and animation, a mouse movement, a visual effect, and anapplication and non-time-based supporting object, such as a text note, atext comment, a highlighting box, a magnifier, a hyperlink, a diagram,and image, and a drawing.

The user database 106 may include one or more databases on one or moreservers for providing and storing any information related to the usersof the information sharing system that 100. Database 106 may include,for example, user profiles in member accounts. The user profiles mayinclude any suitable information related to the user (e.g., demographicinformation, geographical information, online activity history, etc.).In one example, the use of the information sharing system 100 may be“members” who have subscribed for the service of the information sharingsystem 100 and have an associated member account stored in the userdatabase 106. The member account may include records such as annual feespaid to the entity that runs information-sharing system 100 and servicefees incremented per information service and paid to the entity thatruns the information sharing system 100 and/or other members who providethe piece of information (e.g., base objects and/or supporting objects).It is understood that the users may also be “non-members” who can usethe information sharing system 100 as guests without subscribing for theservice from the information sharing system 100. The member account mayalso include records such as a time and date when each base object,supporting object, or synchronizing actions is created and modified bythe member user.

FIGS. 2(a) and 2(b) are more detailed diagrams of the informationsharing system 100 shown in FIG. 1, according to different embodimentsof the present teaching. In FIG. 2(a), a user may interact with theinformation sharing system 100 to provide information in the forms ofbase objects, supporting objects, synchronizing actions, which he/shewould like to share with other users for free or at a price. In thisexample, the user may first upload a user file, which contains contentsto be shared, in any suitable type. The information-sharing controller102 then converts the user file into a base object of a certain type asnoted above. The base object is stored in the information database 104.The user then may comment on the base object by providing add-on text.The information-sharing controller 102 then generates a supportingobject based on die add-on text. In order to associate the supportingobject with the base object, the user may further input a synchronizingaction to the information sharing system 100. For example, the user maymove the mouse cursor on the screen to indicate where the add-on textshould be located on the base object. The mouse movement may be recordedas a synchronizing action by the information sharing controller 102 andstored in the information database 104. In this example, the base objectitself may also be modified by the user. For example, the user maymodify the content of the original user file and upload the modifieduser file to the information sharing system 100 to replace the previousversion of the base object. The information-sharing controller 102 thengenerates the modified base object and stores it in the informationdatabase 104. In one example, different versions of the base object maybe stored in the information database 104 for version control purposes.The number of supporting objects for a particular base object may not belimited. For example, the user may further provide additional add-oninformation to the modified base object as the additional supportingobjects.

FIG. 2(b) shows building a dynamic information-sharing linkage betweenat least two users through the information sharing system 100. The baseobjects, supporting objects, and synchronizing actions may betransmitted between the paired users to achieve information-sharing.Each user may comment on the other party's shared information by addingsupporting objects and synchronizing actions on the base object. In thisexample, one or more users may have local information sharing client 202each including a local database such that the base object and supportingobject stored in the information database 104 may be retrieved andstored in the local database. The information-sharing client 202 mayreside on any suitable device, such as but not limited to, a desktop orlaptop computer, a netbook, a tablet, a smartphone, a game console, aset-top box, Etc. In this example, synchronizing actions may beretrieved and stored in the information sharing client 202 along withthe corresponding base and supporting objects. Once a user dynamicallymanipulates the base object and/or the supporting object throughsynchronizing actions (e.g., moving a highlighting box to a differentlocation on the WORD document), only the dynamically generatedsynchronizing actions (e.g. the mouse movement) need to be transmittedto the other user because the manipulated base object in the supportingobject has already been retrieved and stored in the local database. As aresult, the information sharing between the users is facilitated sincethe amount of data that needs to be transmitted (dynamic synchronizingactions) is minimized. In this example, depending on the type of sharedinformation, a particular service relationship may be establishedbetween the paired users through the information sharing system 100. Theservice relationship includes, for example, teach—student,editor—author, attorney—client, doctor patient, and collaboratorsrelationships, to name a few.

FIGS. 3(a)-3(g) depict exemplary applications of the information sharingsystem 100, according to the different embodiments of the presentteaching. FIG. 3(a) shows interactive and remote learning through theinformation sharing system 100. And one example, a teacher teachesonline or offline with lecture notes (as space objects) and createsonline or offline testing exams and homework assignments (as faceprojects close parentheses. Teachers can also subscribe and make copiesof standard teaching lectures, exams, and homework assignments andfurther customize the lectures, exams, and homework assignments tobetter suit the needs of his or her students. Students can learn onlineor offline by, for example, watching and listening to the lectures andcompleting the exams and homework assignments (as supporting objectsassociated with the base object). The teacher made further reviews andcomments on the student's answers to the exams and assignments by addingadditional supporting objects to the exams and assignments. For offlinelearning, the lectures, exams, and assignments may be delivered andsaved to each student's local information-sharing client 202. As notedabove, the teacher and students may be members of the informationsharing system 100, and the interactive and remote learning establishesa teach-student relationship between the members. The member account inthe user database 106 may track the information sharing/exchange betweenthe teacher and students in order to calculate the service charges thatthe students need to pay to the entity that runs the information sharingsystem 100 and the teacher. For example, the service charge calculationmay be based on the number if the base and/or supporting objectsdownloaded to the student's local information sharing client 202 (e.g.the total pages of lecture notes), the number of course subjects thestudents have subscribed, or the amount of time the teacher and/or thestudents have spent on the interactive and remote learning. It isunderstood that the non-member users of the information sharing system100 may also be able to participate in the learning for free through theinformation sharing system 100 either as the teacher or the student. Inthat case, the teacher may make a profit by adding advertisements on theteaching materials that he/she uploads to the information database 104,and the entity that runs the information sharing system 100 may also addadditional advertisement on the teaching materials to make a profitinstead of charging the students directly. In addition, the students mayprovide feedback and ratings to the teachers and their teachingmaterials, and the feedback may be tracked in the member account as afactor to determine the service fees to be allocated to each teacher.

FIG. 3(b) shows music sharing, learning, and publication through theinformation sharing system 100. In this example, music sheets may beconverted and stored as base objects in the forms of, for example, PDF,flash, or image files, which can be synchronized with supportingobjects, such as instruments music, or songs in the forms of audio orvideo files, add on notes, highlighting, etc. Such a platform powersmusicians and students to cooperate and learn based on the same standardbase objects (the converted sheet music as the base objects). Forexample, the music recordings (as supporting objects) made by musiciansmay synchronize with the music sheets (a space object) and available toother users of the information sharing system 100. For example,musicians can compose and publish their sheet music as standard objects,or record their piano or another instrument playing, and upload theplaying as the supporting objects to the information database 104 sothat other users can share the recorded playing for various purposessuch as entertainment, music learning, or publishing their own recordingwith the professional music accompaniments. The information database 104may contain standard music sheets for the musicians to record and uploadtheir music accompaniments as supporting, objects to the standard musicsheets. Moreover, since the base and supporting objects may be storedlocally instead of being transmitted as the video streaming, the musicsharing and learning in this example can be achieved with minimumlatency.

In this example, the music accompaniment made by famous musicians couldbe featured and available for other users to sing along with words toplay their musical instruments with, at a certain price. This allowsmusicians to publish their records through the information sharingsystem 100 to easily promote and sell their music pieces. It isunderstood that users of the music sharing, learning, and publicationapplication may be either members or non-members, and their monetizationschemes may vary accordingly as noted above. For example, for members,service charges may be incremented for each music accompaniment downloadand tracked in the members' account in the user database 106. In oneexample, the information sharing system 100 may be used to facilitatesuch transactions by splitting the collected service fees between themusicians and the entity that runs the information sharing system 100.

In one example, different users (e.g., musicians) can post theirperformance on a piece of music, and another user can select and chooseto compose different pieces together to make e.g., a symphony. Inanother example, a composer can post his/her music and solicited otherusers to play different instruments and then put them together. Theput-together music may be distributed or downloaded to make a profit. Inthis example, information sharing system 100 keeps track of which pieceis actually incorporated into the final performance and the number ofdownloads. And one example, the entity that runs the information sharingsystem 100 may make a profit by taking a percentage of the income, andat the same time, the information sharing system 100 may keep track ofthe contributors to make sure that they will also get paid because theirprice has been incorporated into the final product. In a similar vein,the information sharing system 100 may generate a sharing object thatcomprises all the information generated from the original base object,which, for example, includes all the modifications of the originalcontent of the user file and all the add on comments, notes,explanations, reviews, etc., in the forms of supporting objects andsynchronizing actions. Such sharing object may have its special value asa new piece of information and may be distributed and downloaded by anyuser. In one example, the base object itself may contain a solicitationto a particular group of users (e.g., collaborators in the same entity)or to all users of the information sharing system 100 contributing tothe sharing object. It is also understood that the application in FIGS.3(a) and 3(b) may be combined such that interactive and remote musiclearning may be achieved through the information sharing system 100.

FIG. 3(c) shows research notes and papers discussion through informationsharing system 100. Research labs often require their research membersto share notes and publications. Research notes are often written in thedocument and word processing file format, such as MICROSOFT WORD, andneed to be shared with other researchers. In this example, theinformation sharing system 100 provides an intuitive and effective wayto achieve research notes and paper sharing among researchers. Forexample, the research note and papers may be generated as base objectsand shared with other members in the research lab. The researcher maycomment on the base object by adding supporting objects in various formsas noted above. Similarly, FIG. 3(d) shows team collaboration throughthe information sharing system 100. In this example, any team member cansave documents, ideas or any information to the information database 104through the information sharing system 100 in order to share theinformation with collaborators. And one example, the base and supportingobjects may be used as the work requirements or work specifications suchthat the team leader or manager can assign the base and supportingobjects to team members as work assignments to manage teamwork. FIG.3(e) shows interactive meetings through the information sharing system100. And in this example the information sharing system 100 may enableusers to conduct an online meeting with minimum latency. For example,during the meeting, the presenter may switch pages of a document,highlight certain areas, play animations, and playback pre-recordedaudio files that are synchronized with page switching or the animation.Because such meetings may only transfer dynamic synchronizing actionswithout sending massive amounts of video stream data, it provides abetter user experience. The interactive meeting will be described indetail later. FIG. 3(f) shows real-time polling and voting through theinformation sharing system 100. In this example, because information canbe shared as base objects, and multiple users can input their notes,comments, and ratings (as supporting objects) for approval ordisapproval, the information sharing system 100 may be applied forreal-time polling and voting with multiple inputs are required inreal-time for making team consent and agreement. FIG. 3(g) showsinformation sharing for social networking through the informationsharing system 100. And in this example, any information Such asdocuments can be easily converted to movie-like presentations as baseobjects by the information sharing system 100. Plus, even users withlittle computer knowledge may produce professional-qualitypresentations. The information-sharing system 100 may be integrated withany other social networking tools for more impressive and effectiveinformation sharing.

FIG. 4 depicts an exemplary diagram of the information sharingcontroller 102 to an embodiment of the present teaching. In thisexample, the information sharing controller 102 includes a base objectgenerator 402, he's supporting object generator 404, and a synchronizingengine 406, each operatively coupled to the information database 104.The base object generator 402 may be configured to convert a user fileto a base object of a certain type such that the information in the userfile is accessible to any user via a web browser or an application. Thebase object generator 402 may reside on a server in the “cloud” or onthe local information-sharing client 202. The base object generated bythe base object generator 402 may be stored in the information database104 directly if the base object generator 402 is in the “cloud” or maybe stored in the local database and uploaded to the information database104 later if the base object generator 402 is on the localinformation-sharing client 202.

The information-sharing controller 102 may also include a supportingobject generator 404 configured to generate the supporting object to beassociated with the base objects in response to user inputs andrequests. As noted above, the supporting objects may include time-basedsupporting objects that are synchronized with the base object in atimescale and non-time by supporting objects that are coordinated withthe base object in the space scale. The supporting objects then may bestored in the information database 104 as separate files from theassociated base objects. Similar to the base object generator 402, thesupporting object generator 404 may reside on a server in the “cloud” oron the local information sharing client 202.

The information-sharing controller 102 may further include asynchronizing engine 406 configured to generate synchronizing actionsfor manipulating and associating the face objects and correspondingsupporting objects. For example, the base objects and supporting objectsmay already exist in the local database of the local information sharingclient 202 where the base and supporting objects are generated or maybepre-downloaded to the local database. Thus, only the dynamically changedsynchronizing actions need to be transferred from the informationdatabase 104 to each user's local information sharing client 202 tocoordinate the presentation of the base and supporting objects on localinformation sharing client 202.

FIG. 5 is a depiction of an exemplary non-time by supporting object 502and time-based supporting object 504, according to an embodiment of thepresent teaching. For non-time-based supporting object 502, those visualobjects are coordinated with the base object 506 by specifying therelative scale coordinates on the base object 506. The base object 506may be represented as a visual object with three dimensions, includingpage numbers representing the z coordinate and the horizontal andvertical coordinates (x, y) Representing a position where thenon-time-based supporting object 502, as shown in FIG. 5. In oneexample, standard resolution/coordinates may be applied for coordinatingthe non-time-based supporting object 502 on the base object 506. Forexample, the information sharing system 100 may use a relative scalemechanism of height and width of the base object 506, allowing thenon-time-based supporting object 502 to be displayed independent ofscreen size or resolution.

For time-based supporting object 504, these objects and the base object506 may be synchronized in a timescale. As shown in FIG. 5, eachtime-based supporting object 504 or each part of a time-based supportingobject 504 may be activated at a correct time as triggered by one ormore synchronizing actions. The synchronizing engine 406 may use time asthe coordinating scale so that any audio, video, mouse movements,animations, visual effects, applications, or any other time-basedsupporting object 504, are recorded with the absolute value of time. Forexample, as a user plays back the recorded audio or animation,synchronizing actions may be used to synchronize the audio or animationwith the base object. The synchronizing actions may include informationregarding, for example, on which page or at what time to activate thetime-based supporting object 504. Synchronizing multiple time-basedsupporting objects 504 may also be supported. For example, recordedanimations may be saved and played back while playing back the audio. Inaddition, time-based supporting objects 504 may be synchronized with avideo-type base object 506. This can be achieved in a way similar to howthe time by supporting objects 504 are handled with respect to thedocument type-based objects 506.

FIG. 6 is a depiction of an exemplary process of synchronizingsupporting objects with a base object, according to an embodiment of thepresent teaching. In this example, different users may add differentsupporting objects, which may be synchronized by time-based coordinatesand/or the three-dimensional space coordinates, as noted above. In thisexample, a version control mechanism may be applied to control themodification of the base object and the association of additionalsupporting objects to the different versions of the base object. Forexample, once a user modifies the content of the user file, the baseobject may be converted again and labeled as a new version todistinguish it from previous versions. And one example, a new supportingobject may be always associated with the latest version of the baseobject. And another example, the supporting objects associated with thelatest version of the base object may, re-associate it with the latestversion of the base object if necessary. It is understood that some orall of the versions of a base object may be temporarily or permanentlystored in the information database 104 and/or local database ifnecessary.

FIG. 7 is a depiction of another exemplary process of synchronizingsupporting objects with a base object, according to an embodiment of thepresent teaching. In this example, not only the base object is versioncontrolled, but also the supporting objects and synchronizing actionsmay be version controlled. In this example, a base object with itsassociated supporting objects and synchronizing, actions may be definedas a sharing object. Any change on the base object, supportingobject(s), or synchronizing action may trigger the information sharingsystem 100 to record a new version of the sharing object. For example,adding new add-on notes and sounds to the sharing object may generate anew version of the sharing object; modifying the base document maygenerate a new version of the sharing object; adding a new synchronizingaction to the previous version may also generate a new version of thesharing object. In this example, the information sharing system 100 mayregenerate each version of a sharing object with the corresponding baseobject, supporting object(s), and synchronizing action(s).

FIGS. 8(a) and 8(b) our flow charts of exemplary processes in whichinformation sharing is performed, according to different embodiments ofthe present teaching. In FIG. 8 (a), starting from block 802, a firstrequest is received from a user to access a first piece of informationin the information database 104. As a response to the first request atblock 804, a first representation of the first piece of information isretrieved. A block 806, the first piece of information is madeaccessible to the user. For example, the information sharing system 100may convert the first piece of information to a base object of a certaintype and present the base object to the user as a response to the firstrequest.

Moving to block 808, a second request to generate a second piece ofinformation based on the first piece of information is received. Atblock 810, the second piece of information is generated based on aninput received from the user. At block 812, a second representation ofthe second piece of information is created. For example, the informationsharing system 100 may receive a second request from the user togenerate a second piece of information, such as a supporting object andor a synchronizing action, based on the base object. Theinformation-sharing system 100 may generate the second piece ofinformation based on the user's inputs and creates a representation ofthe second piece of information so that other users may retrieve thesecond piece of information. In one example, the second representationmay be an indication of the second piece of information available forretrieval, such as a list of supporting objects that are associated withthe first piece of information for selection.

Moving to block 814, the first and second pieces of information arestored, for example, in the information database 104 or local databases.At block 816, the second piece information is associated with the firstpiece of information. At block 818, when the first piece of informationis accessed, the second representation of the second piece ofinformation is retrieved. For example, the second representation in thefirst representation may be marked as associated with each other so thatwhenever the first piece of information is accessed in the future, thesecond piece of information is made available.

In FIG. 8(b), starting from block 820, a first request is received froma first user to access a first piece of information. In response to thefirst request, at block 822, a first representation of the first pieceof information is retrieved. At block 824, a second representation of asecond piece of information created by a second user and associated withthe first piece of information is retrieved. For example, theinformation sharing system 100 may receive a first request from thefirst user to access a first piece of information. In response to thefirst request, the base object and its associated supporting objects andsynchronizing actions created by a second user may be retrieved andpresented to the first user as the first and second pieces ofinformation, respectively. In one example, the representation of thesecond piece of information may include a solicitation for a response tothe second piece of information. For example, the first piece ofinformation may be a music sheet, and the second piece of informationmay be a playing of the music sheet made by the second user with asolicitation to the first user for comment on the playing.

Moving to block 826, a second request is received from the first user tocreate a third piece of information associated with the second piece ofinformation. At block 828, the third piece of information is createdbased on input from the first user. Moving to block 830, a thirdrepresentation is created for the third piece of information. The thirdrepresentation includes an indication of association to the second pieceof information. At block 832, a relationship between the first and thesecond users is established. For example, the information sharing system100 may further receive a second request from the first user to create athird piece of information, such as additional supporting objects and/orsynchronizing actions. The information-sharing system 100th in maycreate the third piece of information and establishes a relationshipbetween the first and the second users. At block 834, once therelationship is established, a record may be created as evidence of therelationship by the information sharing system 100. In one example, thethird piece of information (e.g. comments made by the first user on thesecond user's playing) may be transmitted back to the second user as aresponse to the solicitation for comment.

FIG. 9 is an exemplary diagram of a system for online meetings,according to an embodiment of the present teaching. In this example, thesystem may include a meeting server 900 residing in the “cloud” andlocal meeting clients 902, 904 for the meeting presenter (host) andparticipants (guests). The meeting server 900 may include theinformation database 104 that stores the base and supporting objects andthe synchronization engine 406 operatives to simultaneously dispatchdynamic synchronizing actions (actionable items) received from themeeting presenter 902 to each meeting participant 904. In this example,the base and supporting objects, such as the presentation slides andcomments, maybe pre-downloaded to the local database of each meetingparticipant 904. During the meeting, the presenter 902 made dynamicallygenerated new synchronizing actions by the synchronizing actiongenerator 906, Such as moving the mouse cursor on the presentationslides, highlighting an area, or switching pages. These dynamicsynchronizing actions may synchronize with the base object in supportingobjects and output it to the presenter 902. At the same time, thedynamic synchronizing actions may be simultaneously transmitted to theaction synchronizing module 908 of each participant in real-time.Similarly, these dynamic synchronizing actions may be synchronized withthe base object and supporting objects and presented to each participant904.

For example, in FIG. 10, an object may be presentation slides that havebeen pre-downloaded to the local database of each participant before themeeting starts. At time t11 the presenter may generate a first dynamicsynchronizing action (actionable item) of switching the presentationslides to page 22. The first dynamic synchronizing action may bedispatched to each meeting participant at approximately the same time ofal, such that the presentation slide on each participant's machine mayalso be switched to page 22. At time t12, the presenter may create asecond dynamic synchronizing action of adding an animation note on page22. In one example, the animation that may exist in the local databaseof participant one, and thus, only the dynamic synchronizing actionitself needs to be transferred to participant one to instruct which andwhere the animation needs to be added. However, if participant 2 doesnot have the animation note and its local database, it may retrieve theanimation note from participant 1 or from the information database.Also, the second dynamic synchronizing action may not be directeddispatch from the meeting server to participant to but instead, maybetransmitted from participant 1. As shown in FIG. 10, other dynamicsynchronizing actions, such as moving mouse cursor and highlighting, mayalso be dispatched to the participant in a similar manner as notedabove.

FIGS. 11(a) and 11(b) are flow charts of exemplary processes in whichonline meetings are performed, according to different embodiments of thepresent teaching. In FIG. 11(a), starting at block 1102, a first requestto access the first piece of information is received. The first requestis associated with a plurality of users, e.g. meeting participants 904.The first piece of information may be based on objects and supportingobjects, such as presentation slides, at block 1104, the first piece ofinformation is retrieved as a response to the first request. Theretrieved first piece of information is delivered to the plurality ofusers to become accessible at block 1106. For example, the meetingserver 900 May retrieve the presentation slides from the informationdatabase 102 so that each meeting participant 904 can pre-download thepresentation slides before the meeting starts.

At block 1108, a second request is received from an acting user, e.g.,the meeting presenter 902, to generate a second piece of informationbased on the first piece of information. That block 1110, the secondpiece of information, e.g., synchronizing actions, is generated based onan input received from the acting user. For example, during the meeting,the presenter 902 may dynamically generated new synchronizing actions bythe synchronizing action generator 906, such as moving the mouse cursoron a presentation slides, highlighting an area, or switching pages.Proceeding to block 1112, information indicating an association betweenthe second piece of information and the first piece of information iscreated. For example, dynamic synchronizing actions may synchronize withthe base object and supporting objects as output to presenter 902. Iblock 1114, the second piece of information with embedded informationindicating the association is delivered to the plurality of users. Forexample, the dynamic synchronizing actions may be simultaneouslytransmitted to the actions synchronizing module 908 of each participant904 in real-time.

In FIG. 11(b), before the meeting starts, the meeting's over 900delivers a base object, e.g., presentation slides, to the meetingpresenter 902 in each meeting participant 904 at blocks 1116 and 1118respectively. During the meeting, the meeting server 900, at block 1120,receives input from the meeting presenter 902 to generate an actionableitem for the base objects, such as moving the mouse cursor on thepresentation slides, highlighting an area, or switching pages. At block1122, the meeting server 900 delivers the actual items to all themeeting participants 904 simultaneously, and each meeting participant904 receives the action of item in real-time during the meeting at block1124. The action item has been associated with the base object for themeeting for presenter 902 and meeting participants 904 at blocks 1124and 1128, respectively. The base object with the associated actionableitem is then presented to the meeting presenter 902 and meetingparticipants 904 at blocks 1130 and 1132, respectively.

This online meeting not only allows users to view the same shareddocument but also transfers the synchronizing actions performed by thepresenter to all participants instantly. Since the size of thesynchronizing action data is relatively small, the latency is minimized.As a result, the participants can synchronize action as the meetingpresenter performs them in real-time. It provides a real-time andin-person feeling for the meetings to the end-users. Not having anylatency and providing an in-person feeling promotes a more effectivecommunication tool to its users. In addition, meetings can be recordedand played back by other users so that those people who are not able toattend the meeting live may be at the exact same meeting at a latertime. Furthermore, since the recorded meeting is the synchronized actionsaved in sequential order based on the time scale, such recordedmeetings have a very small file size and provide more advantages overtraditional methods where online meetings are recorded as video fileswith the larger size.

To implement the present teaching, computer hardware platforms may beused as the hardware platform(s) for one or more of the elementsdescribed herein. The hardware element, operating systems, andprogramming languages of such computers are conventional in nature, andit is presumed that those skilled in the art are adequately familiartherewith to adapt those technologies to implement the processingessentially as described herein. A computer with user interface elementsmay be used to implement a personal computer (PC) or another type ofworkstation or terminal device, although a computer may also act as aserver if appropriately programmed. It is believed that those skills inthe art are familiar with the structure, programming, and generaloperation of such computer equipment and as a result, the drawing shouldbe self-explanatory.

FIG. 12 depicts a general computer architecture on which the presentteaching can be implemented and has a functional block diagramillustration of a computer hardware platform that includes userinterface elements. The computer may be a general-purpose computer or aspecial-purpose computer. This computer 1200 can be used to implementany components of the information sharing architecture as describedherein. Different components of the system can all be implemented on oneor more computers such as a computer 1200, via its hardware, softwareprogram, firmware, or a combination thereof. Although only one suchcomputer is shown, for convenience, the computer functions relating toinformation sharing may be implemented in a distributed fashion on anumber of similar platforms to distribute the processing load.

The computer 1200, for example, includes COM ports 1202 connected to andfrom a network connected there to facilitate data communications. Thecomputer 1200 also includes a central processing unit (CPU) 1204, in theform of one or more processors, for executing program instructions. Theexemplary computer platform includes an internal communication bus 1206,program storage and data storage of different forms, e.g. disc 1208,read-only memory (ROM) 1210, or random access memory (RAM) 1212, forvarious data files to be processed and or communicated by the computer,as well as possibly program instructor to be executed by the CPU. Thecomputer 1200 also includes an I/O component 1214, supportinginput-output flows between the computer and other components thereinsuch as user interface elements 1216. The computer 1200 may also receiveprogramming and data network communications.

Hence, aspects of the method of information-sharing, as outlined above,may be embodied in programming. Program aspects of the technology may bethought of as “products” or “articles of manufacture” typically in theform of executable code and/or associated data that is carried on orembodied in a type of machine-readable medium. Tangible non-transitory“storage” type media includes any or all of the memory or other storagefor the computers, processors or the like, or associated modulesthereof, such as various semiconductors memories, tape drives, discdrives, and the like, which may provide storage at any time for thesoftware programming

All or portions of the software may at times be communicated through anetwork such as the Internet or various other telecommunicationnetworks. Such communications, for example, may enable loading of thesoftware from one computer or processor to another. Plus, another typeof media that may bear the software elements includes optical,electrical, and electromagnetic waves, such as used across physicalinterfaces between local devices, through wired and optical landlinenetworks, and over various Airlink. The physical elements that carrysuch waves, such as wired or wireless length, optical links, or thelike, may be considered as media bearing the software. As used herein,unless restricted to tangible “storage” media, terms such as computer ormachine “readable medium” refer to any medium that participates inproviding instructions to a processor for execution.

Hence, a machine-readable medium may take many forms, including but notlimited to, a tangible storage medium, a carrier wave medium or aphysical transmission medium. Non-volatile storage media include, forexample, optical or magnetic disks, such as any of the storage devicesin any computer(s) or the like, which may be used to implement thesystem or any of its components as shown in the drawings. Volatilestorage media include dynamic memory, such as a main memory of such acomputer platform. Tangible transmission media include coaxial cables,copper wire, and fiber optics, including the wire that form a bus withinthe computer system. Carrier wave transmission media can take the formof electric or electromagnetic signals or acoustic or light waves suchas those generated during radio frequency (RF) and infrared (IR) datacommunications. Common forms of computer-readable media, therefore,include an example: a floppy disk oh, a flexible disk, hard disk,Magnetic Tape, any other magnetic medium, A CD-ROM, DVD, or DVD-ROM, orany other optical medium, punch card paper tape, any other physicalstorage medium with patterns of holes, a RAM, a PROM, and EPROM, andFLASH-EPROM, and any other memory chip or cartridge, a carrier wavetransporting data or instructions, cables are links transporting such acarrier wave or any other medium from which computer can readprogramming code and/or data. Many of these forms of computer-readablemedia may be involved in carrying one or more sequences of one or moreinstructions to a processor for execution.

In addition to the above identified features, options, controls, andcomponents, system 10 may also include other features andfunctionalities, among other options, controls, and components.

It will be appreciated by those skilled in the art that other variousmodifications could be made to the system, process, and method of usewithout parting from the spirit and scope of this disclosure. All suchmodifications and changes fall within the scope of the claims and areintended to be covered thereby.

What is claimed:
 1. An information sharing system, comprising: aplurality of collaborators; a content; a sync; the sync having at leastone content; the sync having a voice recording; the voice recordingcreated by the plurality of collaborators; the voice recording overlaidover the content so that the content is being discussed in the voicerecording; wherein the voice recording communicates information anddiscussion related to the content; wherein the voice recording providesadditional information related to the content; the sync having aplurality of annotation features; the plurality of annotation featurescreated by the plurality of collaborators; the plurality of annotationfeatures overlaid over the content so that the content is beingdiscussed and emphasized by the plurality of annotation features;wherein the plurality of annotation features communicates informationand discussion related to the content; wherein the plurality ofannotation features provides additional information related to thecontent; wherein the sync can be viewed in a similar manner to viewing avideo; such that the information shared within the sync can be revieweda number of times if needed.
 2. The system of claim 1, furthercomprising: a subsequent sync edit; wherein the subsequent sync editcreates a second sync.
 3. The system of claim 1, further comprising: ahistory log; the history log having a viewable log of the sync andinteractions between the sync and the plurality of collaborators:wherein any one of the plurality of collaborators can review originalsyncs which were created; wherein any one of the plurality ofcollaborators can review subsequent syncs created; wherein the pluralityof collaborators can quickly review a history of a topic to understandthe history of a communication about the content.
 4. The system of claim1, further comprising: a first collaborator; a second collaborator;wherein the first collaborator creates a first sync; wherein the secondcollaborator views the first sync at a time subsequent to the creationof the first sync by the first collaborator.
 5. The system of claim 1,further comprising: a first collaborator; a second collaborator; whereinthe first collaborator creates a first sync; wherein the secondcollaborator views the first sync at a time subsequent to the creationof the first sync by the first collaborator; wherein the secondcollaborator creates a second sync; wherein the first collaborator viewsthe second sync at a time subsequent to the creation of the second syncby the second collaborator.
 6. The system of claim 1, furthercomprising: a syncroom; the syncroom having a plurality of syncs; thesyncroom having a plurality of syncs related to the same topic.
 7. Thesystem of claim 1, further comprising: a syncroom; the syncroom having aplurality of syncs; the syncroom having a plurality of syncs related tothe same topic; the syncroom having a chat feature; the syncroom havinga meeting launch feature; the syncroom having a livesync launch feature;wherein the syncroom provides access to a plurality of syncs related tothe same topic; wherein the syncroom provides for information sharing,on the same topic.
 8. The system of claim 1, further comprising: aninformation sharing controller; an information database; a collaboratordatabase.
 9. The system of claim 1, further comprising: an informationsharing controller; an information database; a collaborator database; aninformation sharing client.
 10. The system of claim 1, furthercomprising: a base object generator; a supporting object generator; asynchronizing engine.
 11. The system of claim 1, further comprising: abase object generator; a supporting object generator; a synchronizingengine; a non-time-based supporting object.
 12. The system of claim 1,further comprising: a base object generator; a supporting objectgenerator; a synchronizing engine; a time-based supporting object. 13.The system of claim 1, further comprising: a base object generator; asupporting object generator; a synchronizing engine; a plurality of baseobjects.
 14. The system of claim 1, further comprising: a meetingserver; a plurality of local meeting clients; a synchronizing generator;a synchronizing module.
 15. The system of claim 1, further comprising: acomputing system; a plurality of corn ports; a central processing unit;an internal communication bus; a storage; a random access memory; an I/Ocomponent; a user interface.
 16. A collaboration and communicationsystem, comprising: a plurality of collaborators; at least one content;a livesync; the livesync having at least one content; the livesynchaving a voice feature; the voice feature spoken by at least one of theplurality of collaborators; the voice feature spoken for the purpose ofaudio communication over the content so that the content is beingdiscussed in the voice feature; wherein the voice feature communicatesinformation and discussion related to the content; wherein the voicefeature provides additional information related to the content; thelivesync having a plurality of annotation features; the plurality ofannotation features created by the plurality of collaborators; theplurality of annotation features providing real-time annotation on thecontent so that the content is being visually discussed and emphasizedby the plurality of collaborators; wherein the plurality of annotationfeatures communicates information and discussion related to the contentin real time; wherein the plurality of annotation features providesadditional information related to the content in real time; wherein thelivesync can be viewed in a similar manner to viewing a video; such thatthe information shared within the livesync can be reviewed a number oftimes if needed; wherein the plurality of collaborators are able toeffectively communicate and share information in real-time throughannotation, voice communication, and a chat feature.
 17. The system ofclaim 16, further comprising: a first collaborator; a secondcollaborator; wherein the first collaborator creates a first livesync;wherein the second collaborator views the first livesync at a time ofcreation of the first livesync by the first collaborator; such that thesecond collaborator is viewing the livesync in real-time; such that thesecond collaborator is interacting in information sharing with thelivesync;
 18. The system of claim 16, further comprising: a firstcollaborator; a second collaborator; wherein the first collaboratorcreates a first livesync; wherein the second collaborator views thefirst livesync at a time subsequent to the creation of the firstlivesync by the first collaborator; wherein the first collaboratorcreates a first livesync; wherein the second collaborator views thefirst livesync at a time of creation of the first livesync by the firstcollaborator; such that the second collaborator is viewing the firstlivesync ill real-time; wherein the second collaborator interacts withthe first livesync by providing voice and annotations on the firstlivesync; wherein the second collaborator creates a second livesync. 19.The system of claim 16, further comprising: a syncroom; the syncroomhaving a plurality of livesyncs; the syncroom having a plurality oflivesyncs related to the same topic; the syncroom having a chat feature;the syncroom having a meeting launch feature; the syncroom having alivesync launch feature; wherein the syncroom provides access to aplurality of livesyncs related to the same topic; wherein the syncroomprovides for information sharing on the same topic.
 20. A method ofcollaborating and communicating, comprising the steps: opening a contentin a sync; the content uploaded into the sync by a first collaborator;recording voice to create a video for a sync; annotating the contentduring the video of the sync; sharing the sync with a secondcollaborator; viewing the sync by the second collaborator.